Summary

Implements modelcontextprotocol/modelcontextprotocol#1034 by adding optional default value support to StringSchema, NumberSchema, and EnumSchema in elicitation schemas.

Motivation

Resolves #521

Currently, users must manually enter information that could be pre-populated with sensible defaults, creating unnecessary friction in interactive tool workflows. For example, in an email reply tool, recipient and CC information from the email thread context should be automatically populated rather than requiring manual re-entry.

Changes

• StringSchema: Added optional default: Option<Cow<'static, str>> field with with_default() builder method
• NumberSchema: Added optional default: Option field with with_default() builder method
• EnumSchema: Added optional default: Option field with with_default() builder method
• Added comprehensive test coverage (8 new tests) for default value serialization, deserialization, and backward compatibility
• Updated elicitation_stdio.rs example to demonstrate default values usage in a practical email reply scenario

Implementation Details:

• Follows the existing BooleanSchema pattern for consistency
• All defaults are optional (Option) for backward compatibility
• Uses #[serde(skip_serializing_if = "Option::is_none")] to ensure old clients can safely ignore the new field
• Type-safe: Rust's type system ensures defaults match their schema types

Example Usage

  let schema = ElicitationSchema::builder()
      .string_property("recipient", |s| {
          s.format(StringFormat::Email)
              .with_default("[email protected]")
              .description("Email recipient")
      })
      .number_property("confidence", |n| {
          n.range(0.0, 1.0)
              .with_default(0.8)
              .description("Reply confidence score")
      })
      .build()?;

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed